New Features in VoiceConsole 6.4
Operator Privacy Consent
The customer must collect operator privacy consent for operators within a VoiceConsole SaaS deployment. Consent collection is optional in an On Prem deployment. VoiceConsole provides a method to collect and track consent. The Operator Privacy Notice can be viewed at help.honeywellaidc.com/privacy/Content/Privacy.htm.
VoiceConsole consent collection functions as follows:
-
Consent collection is required for VoiceConsole SaaS deployments.
-
Consent collection is optional for VoiceConsole On Prem deployments and can be enabled in System Configuration.
-
Consent collection is optional for VoiceConsole Hybrid deployments. Customers may be required to collect consent if connecting devices to other solutions.
-
Consent collection is tracked within VoiceConsole.
-
Operators may provide consent via:
-
Kiosk: A link and One time Password (OTP) are provided from VoiceConsole. The operator uses this link and their OTP to provide consent.
-
Mobile Device: When implemented at device level, the operator is asked to provide consent on the mobile device if not already provided. See below for device support.
-
-
Consent is valid for 18 months from the date of collection.
-
VoiceConsole only tracks consent. VoiceConsole does not limit any operator functions based on consent. However, mobile voice devices may check that the operator has completed the privacy consent within VoiceConsole (when required) and can block the operator from certain functions until consent is provided. See below for device support.
Device Support for Privacy Consent
Device consent collection and enforcement requires software upgrades. This function is added with DevKit 2.4 for Android devices. Refer to DevKit Release Notes and online help for details. This function is to be included in a future Voice Catalyst release. Refer to VoiceCatalyst Release Notes for availability.
License Details
-
VoiceConsole displays channel partner and customer names as part of the license information displayed on the upper right corner of the screen.
-
The channel partner and customer information is also displayed on the Configure License screen for Local Licensing in VoiceConsole On Prem deployments after the license is imported.
-
Additional details are displayed in the license table when using Local Licensing in VoiceConsole On Prem deployments.
-
Total, available, and used license counts are displayed in the table.
-
License that are not yet active or that have expired are now displayed in the license table.
-
Automatic Operator Creation
This feature creates a new operator within VoiceConsole when an Android application connects with an operator that does not currently exist in VoiceConsole.
This feature is only supported in a VoiceConsole SaaS deployment and for certain applications. When available with an application, this option can be enabled in System Configuration. To determine if this feature is supported in your environment, review the Release Notes for the specific Android app. Contact Honeywell Customer Support for further assistance.
This feature has limited availability. Honeywell recommends using REST APIs or other standard methods to create operators to ensure better control and integration.
Android Device Config
The previously labeled Device Config option is now Android Device Config
This option generates a OnetimeStartupSettings.config file for the Android device.
Enhanced Template Display
The operator template display is enhanced to display additional template information including the Pick Up & Go (PnG) template type.
The information can also be sorted or filtered by:
-
Language
-
Recognizer
-
Audio Path (device type)
This feature requires device software updates to provide full functionality:
-
For Android devices, refer to future DevKit Release notes for details.
-
For Talkman devices, refer to future VoiceCatalyst Release notes for details.
Log Files
The following log file enhancements are included.
-
To provide parity with Enterprise Voice, log files from DevKit based applications are transferred from the DevKit application to VoiceConsole as a single zip file attachment rather than individual files. DevKit 2.5 is required for this functionality.
-
When log files that are sent from a device VoiceConsole maintains the file name. Previously all log files were identified with a timestamp name.
User Agreements
New users added to a VoiceConsole On Prem deployment are presented with the following items:
-
Honeywell Voice Automated Solutions - End User License Agreement
-
Honeywell voice Automated Solutions - End User Privacy Notice
The user must accept/agree to each before continuing.
This was implemented for users in a VoiceConsole SaaS deployment in VoiceConsole 6.3.2.
Device Support
Support is added for A700XP in On Prem and SaaS deployments. VoiceConsole supports configuring WPA3 and 6 GHz for this device. VoiceCatalyst 5.0 or later is required for A700XP.
VoiceConsole continues to support the following devices:
- A500 (On Prem deployments only)
- A700 (On Prem deployments only)
- A700x
- Android devices - Refer to DevKit documentation for details
Application Support
DevKit-Based Applications
-
Applications must be built from DevKit 1.15 or later. DevKit 2.1 or later is recommended.
- DevKit based applications are licensed through VoiceConsole. The license to run DevKit based applications is separate from the license to develop applications with DevKit. A separate license may be required for GWS Connector. The application is licensed with VoiceConsole 6.x. This allows any supported device to use the license. VoiceConsole 5.x licensed the device, so a different device required a new license.
DevKit based applications are built from DevKit and may be referred to as Guided Work Solutions or branded for a specific solution such as a WMS. These applications run on multiple device types including A700x, A700XP, and Android devices.
VoiceArtisan and Task Builder Applications
- Directed work applications are built from TaskBuilder and VoiceArtisan. These applications run on A500, A700, A700x, and A700XP.
- Honeywell continues to support TaskBuilder and VoiceArtisan based (directed work) solutions for A500, A700, A700x, and A700XP. A DevKit based license is required to support these devices and applications on VoiceConsole 6.1 and later, even if the customer is not currently using a DevKit based application. Also, note that A500 and A700 are supported only in VoiceConsole On Prem deployments.